home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
qbbs
/
zipcount.zip
/
ZIPCOUNT.DOC
next >
Wrap
Text File
|
1990-07-19
|
3KB
|
87 lines
Zipcount Version 1.00
By Arturo Batista of 1:135/79
Introduction:
First, I must say that ZIPCOUNT is guaranteed to do nothing more than
take space in your drive, and that I will not be held liable for any
damage caused or apparently caused by ZIPCOUNT. Use it at you own risk.
History:
Zipcount is the direct offshoot of another simple utility of mine called
LOGZIP. I wrote LOGZIP to time stamp my many logs at the end of each day
and zip them all into one master file. That way all would be centrally
located and already automatically divided into daily chunks to
facilitate searching thru them.
However, I also wanted to consolidate some of the functions of
other utilities that were cluttering my BBS directory. Thus ZIPCOUNT was
conceived. It combines the fuctions of LOGZIP, an RA download counter,
and an FD files request counter. Previously I had several programs doing
this, now they are combined in ZIPCOUNT.
Usage:
ZIPCOUNT requires that PKZIP.EXE be in the dos PATH. It will
automatically search the path for PKZIP.EXE, and will abort if it can
not find it.
ZIPCOUNT is very simple to use. It needs at least two command line
parameters, but a maximum of three as follows:
ZIPCOUNT [1] [d:\path] [d:\path]
Parameter #1 is a code to tell ZIPCOUNT what type of log it is
processing and what action to take. The codes could be one of three:
R would mean and Remote Access Fd style log, and count the downloads.
In a case like this, when a download is found, Zipcount will search the
corresponding files.bbs and if it contains an entry for that file, the
counter is incremented by one. If that entry is not found in the
files.bbs, ZIPCOUNT assumes that that file does not reside in that
directory anymore and ignores that particular download.
F works exactly the same as above except that the search patterns are
altered to find file request in an FD style log. The way that the
files.bbs is handled is basically the same, plus if a files.bbs does not
exist for a file request, the freq is ignored too. That is to handle
those file request from separate areas where the bbs does not access.
Z tells ZIPCOUNT to just time/date stamp the log and zip it.
The second command line parameter is the full pathname of the logfile to
process. I.E. C:\RA\RA.LOG.
These first two parameters are required, as a minimum for ZIPCOUNT to
work. A third parameter may be pass (optional) to have ZIPCOUNT archive
the logs to a given file. As an example, suppose I want to process
c:\ra\ra.log and c:\fd\fd.log and then archive them to c:\logs.zip,
then I would use the following:
ZIPCOUNT R C:\RA\RA.LOG C:\LOGS.ZIP
ZIPCOUNT F C:\FD\FD.LOG C:\LOGS.ZIP
After the logs are processed they are renamed in the following manner:
RA.log would become RAMMDD.LOG, where MM is the month and DD is the day
of the month.
Also if you type ZIPCOUNT<CR>, you will get a comprehensive help screen.
Registration:
If you believe this is worth anything, let me know by sending a
small fee ($5.00 or less) to:
Arturo Batista
575 w 69th Street #107
Hialeah, FL, 33014
All suggestions for later versions and bug reports should be sent to the
above address or NETMAILED to ENTERPRISE!, FIDONET 1:135/79
Arturo